Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1600

reference
502-tree-1
name
1600
tree-preservation-order

undefined

502-tpo-1
uprn
address-text
point
POINT (-1.037214 50.886437)
geometry
MULTIPOLYGON (((-1.037157 50.886431,-1.037160 50.886443,-1.037168 50.886453,-1.037180 50.886461,-1.037196 50.886466,-1.037213 50.886468,-1.037231 50.886466,-1.037247 50.886461,-1.037260 50.886453,-1.037268 50.886443,-1.037271 50.886432,-1.037268 50.886421,-1.037261 50.886411,-1.037248 50.886403,-1.037232 50.886398,-1.037215 50.886396,-1.037197 50.886398,-1.037181 50.886403,-1.037169 50.886410,-1.037160 50.886420,-1.037157 50.886431)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL